The book seems to be written by a bunch of programmer who wrote some explanation around some of their already existing code.

Problem is that the book is so poorly indexed, that even though it covers examples in many subjects, unless you are willing to thumb through the entire book each time you need to look something up ... you won't find it.

Examples include: parameterized queries, combo boxes and even tool tips. Items such as these are covered, but not indexed, making the book almost useless as a reference guide. The book seems to cover a few high level subjects, without discussing much of the necessary foundation ground work of C#/Microsoft programming.

I'd like to say that the code examples are the best part about the book. Also, it seems that the introduction started out very well, providing a great overview of ADO.NET. Yes, and XML, web forms, windows forms, web services/SOAP, and other useful sounding technologies are covered.

The book's documentation of the code, however, was very disappointing. It seems as though someone wrote the code, and someone else did their best to document the code. And did a poor job at that. There were too many generalized one liners for very important snippets of code. And the documenter seems to ramble from generalized explaination to explaination. It also, seems as though the vs.net environment was heavily de-emphasized to the point of doing busy work. For example, at one point the book discusses typing a data bound XML schema into a schema document without describing the XML hierarchy that uses complex and choice elements.(You wonder, "is this required every time I want to render a database in vs.net using XML?"). Just to find out by hunting around in the vs.net GUI that you can drag and drop the database table directly from server explorer to the schema and have the XML identically rendered--taking less than a minute to do so(realizing at the same time that vs.net creates the XML schema that way so it can work with the data effectively).

If you want to learn ADO.NET in a concrete and complete fashion, you're better off starting with Microsoft Q article Q313590 that will point you to even more informative ADO.NET Q articles... (WROX, please learn something from the clarity and brevity and completeness of these Q articles) Otherwise you may be tempted to scower this book to search through its pages hunting for clues that it simply does not contain--wasting precious time for catching up on new technologies.

My hat's off, though, to whoever really wrote the code examples. There's definitely plenty to learn from there from both a C# and ADO.NET perspective. However, you're better off simply downloading the code from the Wrox site for free and stepping through it in a vs.net project. They really did a reasonable job packaging the code for ready utilization.

I did give the book two stars. That's because I paid 60 dollars for it. Please add a star for each additional 12 dollars taken off the book. At 24 dollars, this book would be five stars. It does contain valuable code samples and good introductory information. Unfortunately, I'm having to put the book aside because learning is faster, more efficient, and easier to memorize with Microsoft's Q articles and vs.net's help documentation. Sorry WROX, I love to love your stuff, but your programmers need to add writing to their already wonderful skillset. You could try catching this, though, in author review...before the book is published.

Data-Centric .NET Programming with C#.

This book is about using .NET technologies to work with data, since data can reside in different forms at different places, this book focuses on :

1.Databases.
2.XML / XSL.
3.Directory Services.
4.Messaging Services.
5.Files.
6.Legacy Systems.

Spends 4 chapters on "Databases", 2 on "XML/XSL", 1 on "Directory Services", 1 on "Messaging Services" and 1 on "Files/Registry". Rest of the book contains a chapter on "Web Services" and 3 very useful case studies.

Now just in case if you are an ASP.NET developer and are wondering if there is something in it for me, the answer is "yes and no". I said "yes" because you'll learn how to work with different forms of data and I said "no" because you won't learn anything specifically related to ASP.NET in it. All the code examples that are given only marginally touch ASP.NET ( and that also mainly "Web Services" ), they mostly make use of GUI clients and programs to do all the processing. This is one important thing you should keep in mind, if you haven't developed any GUI client applications ( like me ), there is going to be lot of new stuff for you. Now this is not something bad, as after reading this I not only learned how to work with data but also "how to build GUI clients using C#". Having said that if you know a bit of ASP.NET, you can change the applications from GUI front-ends to ASP.NET pages with little effort.

The topics that this book covers are pretty huge and would take separate books to be discussed thoroughly. But I think that the Wrox team has done an excellent job by covering them in a single book.

The chapters on ADO.NET cover topics like 'what is ADO?', 'how does ADO compare to ADO.NET?', 'OleDb and SqlClient Namespaces', 'DataSet, DataReader and DataAdapter classes', 'Connected and Disconnected Data', 'ADO.NET and XML', 'Using Visual Studio to build Windows Forms', 'Displaying, Editing, Inserting and Deleting Data', 'Connection Pooling', 'Integration with COM+', 'Object Pooling', 'Distributed Transaction Processing' and 'Serviced Components in .NET'.

The chapters on XML/XSL cover topics like 'Using MSXML', 'System.XML Namespace', 'Reading and Writing XML files', 'Creating Windows Forms to Display and Edit XML Data', 'Validating XML', 'XML and ADO.NET', 'Schemas', 'XPath and XSLT' and 'Navigating and Transforming XML'.

The chapter on Directory Services includes topics like 'What is Directory Service?', 'What can Directory Services be used for?', 'System.DirectoryServices Namespace', 'Accessing Directory Services', 'Windows Client Application', 'Accessing the Active Directory', 'Using ADSI', 'Searching', 'Publishing Services', 'Deleting the Service', 'Registering the Service' and 'Searching the Service'.

The chapter on Messaging Services includes topics like 'What are Messaging Services?', 'Where to use Messaging Services?', 'Message Queuing Features', 'Message Queuing Architecture', 'Message Queuing Administrative Tools', 'Programming Message Queuing', 'System.Messaging Namespace', 'Creating Message Queues Programmatically', 'Finding a Queue', 'Sending Messages to Queues', 'Receiving Messages from Queues', 'Transactional Queues', 'Queued Components' and 'COM+ Services'.

The chapter on Files, Serialization and Registry Operations contains topics like 'System.IO Namespace', 'Reading and Writing data to files', 'Synchronous and Asynchronous Data Access', 'Cryptography', 'Isolated Storage', 'Object Serialization', 'XML Serialization' and 'Registry'.

All in all this is a very good book and I give this book 4/5 points and recommend it to any developer seriously interested in .NET C# programming.

This book is a complete study guide for the major structural topics and questions for the architectural licensing exam. My overall enthusiasm for this book was average. I found that there were chapters that were too vague or simply did not have enough information on specific equations. I also found that I did have to supplement the studying from this book with my own notes from my structures courses along with additional study material from other sources. I do recommend this book for anyone wishing to brush up on thier studying for the Lateral Forces and General Structures portions of the ARE/NCARB. Keep in mind, as with any other division of the exam, this would not be a single source for study material.

I found the Ballast guides to be concentrated specifically on the exams that we are acutally going to take. The subjects were organized and concise. Not too much time was spent on "advanced" topics not necessary for the structural topics tested in the exam. It provided most of the rules of thumbs that can be used by architects not only for the exam, but everyday practice. One could purchase the guide strictly as a desk side companion.

This book offers a great summary of the main issues tested in the A.R.E. Although it should not be used as the only resource to study from, it explains most of the terms in a clear and concise manner. Be forewarned, the book does not provide enough information to pass any of the 9 parts. The test taker must use other resources to find and understand all of the required information to prepare successfully for the exam.

I bought this book becouse the reviews were good... Not enough reviews I think, the book itself is not a big thing. Just TCP/IP principles, access lists and something about pix configuration. Could be better. If you want principles, you got them, is easy reading...

I bought this sight unseen and have found it to be delightfully easy to read and understand. Many examples are included to help with the principals and strategies articulated within the book. I'm not one of those that can read some of the Cisco press books cover to cover and get it. So I found it quite refreshing and helpful. Those Cisco techno geeks may be feel its too elementary, but it was just what I wanted. The price is very high, but, for me, it was worth it.

the adfhe a fad; af df ajfd ; af d;fja; a;fdj;af dahd.faf

One of the first things I read by Gogol was "Dead Souls" - and I was enchanted. These stories pale by comparison. (The translation may have something to do with that). Vol.II is better than Vol.I: it contains the true classics, like the "Overcoat". Still, I would recommend reading "Dead Souls" if you want to get a vivid impression of Gogol's genius.

the language of the stories is a little stilted, but it is tough to tell if that is gogol's fault or that of his translator (it is definitely time for a new translation). the stories range in all types and quality, though gogol is at his best when leaning towards the fantastique (kafkaesque comes mind). there are some good stories in the collection: diary of a madman (the only story that is genious), the portrait (gogol ruins what would have been his greatest story with a poorly written, unneccesary second half), the nose, the overcoat, and taras bulba (though a bit wordy and does carry on a little too long). vol 2 is by superior volume (if the editor's introduction and diary of a madman had been in it, there would be no point to volume one).

This publisher has collected in two volumes all of Gogol's short stories. Volume 1 contains Gogol's early work, including his first two books of stories. Several of the stories are good, but there are only two real gems here: "Ivan Schponka and His Aunt" and "Diary of a Madman." Volume 2 contains the real classics: "The Nose", "The Overcoat", etc.

Rather than resolve the authority divide among dissenting groups in this age when sound doctrine is the resisted way (2 Tim. 4), this work of two veteran church growth consultants suggests a famous marketing solution: General Motors.

If you don't like Chevy, there is Buick. If not Buick, then Pontiac, and so on. Here, applied to sociological categories of every 19 year grouping, if don't like Builder's way of doing the faith, try Boomer's. If not Boomer's, then Gen X. Put these all together under one roof, one modified name to make all happy and one leader, and you have their solution: TriGen Church.

Rather than bridge generation gaps which have always been around and were bridged with putting oneself and one's own desires and needs subservient to Christ's, this GM approach is offered to bring the Burger King "have it your way" church, but do it together to have economic and sociologic scale gains under one united, generation combining effort.

Sounds good enough to Builders, Boomers and GenXer's (who buy into what sociology and market research finds from trend and interview research), but is it Biblical?

This reviewer finds it terribly the opposite. Christ wants all to be one under His leadership. He gives undershepherds (pastors) Ephesians 4 to be His Servants of the Word to make this happen gathering around the precious means of grace, Word and Sacraments. This drives it all!

Why change what God wants done? Well, the answer comes back. The people, a sizeable number of them reject this. Of course, and His Word predicts an increasing number will as we near the end.

This book ignores the Biblical mandate for faithful preaching and teaching and pastoral leadership, and inherits worldly ways of coping with serious spiritual maladies.

I understand how reviewer Rodboomboom arrived at his conclusions in his review above. However, I think he missed the point of the book entirely. Is a hymn holy and sacred because of its style or because of the words in it? If you answer that a hymn is sacred because of its style then you will agree with Rodboomboom's review of this book. However, if you understand a hymn to be sacred because of the words of the hymn, not the style, then you will understand the true value and meaning of this book.
Lets say that 5 composers decide to write a song using the exact same wording from John 3:16. Each of them uses a different style of music (hymn, country, classical, rock, and rap) but the wording is identical. Which version of John 3:16 would you listen to? Personally I would not listen to the rap version. That style of music is almost totally repulsive to me. So if someone were to try to present John 3:16 to me using the "rap" version I would not listen. Why? Because I reject the message of John 3:16? NO!!! I reject the form the message came to me. Put John 3:16 in a hymn, classical or rock version and I'm listening (like rap, I wouldn't listen to the country version either).
Am I wrong for not listening to John 3:16 in a country or rap version? Am I refusing to hear "sound doctrine" if I won't listen to it in these forms? The problem that many churches have today is that they offer John 3:16 only in the "rap" version (OK, not specifically but follow the illustration here). And the people often view my not coming to their church as my rejection of the gospel. They may also believe that the "rap" version of John 3:16 is God's version of 3:16. Let's be honest folks, how many times do you choose to listen to a radio station that plays music you don't like? Why do churches demand every generation to like the gospel packaged in a way that one generation has dictated as God's way? And I'm not talking about taking communion with soda and potato chips. The message of the Gospel can remain the same even though its delivery is different. I don't preach in the same language as the Apostles did. Am I compromising the message or not being "subservient to Christ's desires?" Am I not "under Christ's leadership" because I no longer use those languages? The form can and should change. The message should remain the same.
This book teaches how to present the unchanging Gospel in a way that people will want to listen and in a way they can understand (I don't understand what most rap songs are saying). It does not teach how to dilute the Gospel message so that those not wanting to listen will (2 Tim 4). It does teach us how to become all things to all people that we might save some (1 Cor. 9:22). It teaches us to be a church that is not biased to the ways and preferences of one generation (even though that generation may believe their way is the right way). This is a great book for those concerned about reaching all people (regardless of their generational differences) with the saving Gospel of Jesus Christ. And it is a book about how to offer "faithful preaching and teaching and pastoral leadership" that changes lives.

Bob Whitesel and Kent Hunter in "A House Divided" have addressed the difficult issue that has divided the church for many years. They have taken the information we have known for some while about the three generations addressed in the book and applied that information in creative ways to bridge-building over the generational gaps. Their concept of the Tri-Generational Church as a holistic congregation offers much needed hope to the body of Christ in our time. They provide practical descriptions of the necessary leadership style and worship that will work in the Tri-Gen Church. This book is touching a nerve in the church and will make a positive thrust for the outreach and mission of the church. Wm. Leroy Wise, Pastor of Calvary United Methodist Church, Syracuse, IN

I have been kickboxing for fifteen years, and got this book in the hopes that it would offer some fresh perspectives on the subject. I was sorely disappointed.

The book has a kernel of good information, however, the stances, footwork, combinations and technique demonstrated are so clearly incorrect, I was surprized this book got published. Not only are the authors demonstrating poor technique, the layout and structure of the book doesn't facilitate clear instruction on the principles of fighting.

I realize that this book's bent is JKD kickboxing, however, I wouldn't use this book for anything other than a primer on how NOT to do martial arts.

Perhaps I got spoiled. When I first started fighting back in the 80's, I was lucky enough to get a copy of Jean-Yves Theiriault's "Full Contact Karate". This book has become a collectors item. When I see books like the one I just reviewed, I understand why people are willing to shell out [price] for a used copy of Theiriault's book.

Jeet Kune Do Kickboxing is a good overview of the basics of Jun Fan Gung Fu in the kicking and punching range. If you're already a Jun Fan / JKD student under a qualified instructor you probably won't get anything really new out of this, but it is a good reference for those of us who aren't good about taking notes. My only complaint is that the basic stance and footwork are only given about a page and a half, and IMO, those are two of the absolute most important things as they are the foundation for everything else. If you don't have a good stance and good footwork, everything else falls apart.

a very good photo book that showing and explaining the kickboxing of jeet kune do, plus including many boxing and kickboxing drills(including how to train with the partner wich this particular part of the book is superb).the 5 ways of attack (in the art of jeet kune do) are explained in the application of j.k.d.-kickboxing wich is the topic of this book.a very technical book with explanations,although the footwork (as my previous reviewers mentioned) should have to be disccussed more in details.in short it is recommanded !

Of the dozens of Harlequin Temptations and Blaze romances I have read, this is probably the worst. I'd guess the author is trying to emulate Sex and the City, but falls far far short. Every page has howlingly bad writing (I'd give examples, but I left the book at the beach) and the characters' motivations literally make no sense. Worst of all, flat and unbelievable sex scenes. What happened to the editors at Harlequin?

This book is the first in a series about a group of 6 young women who successfully started an internet site in California. Macy is the main character in this book and is a self-proclaimed "wild child" who does not want to grow up. This image is further abetted by her fashion style - dressing like a teenager, which compounds the childish appearance of her body and face. Macy hooks up with lawyer Leo, who is a stuffed shirt who barely smiles, let alone is interested in having a "wild" lifestyle. What do they see in each other? Cheap sex is all they have in common as far as I can tell. The author's goals were too ambitious for this first novel in the series and the story would have been greatly improved by judicious editing. There were too many details that were extraneous to this story and future installments, for example, paragraphs were spent on describing the food at Macy's parties and the interactions between the other and men at the parties. I suppose the latter was designed to pique interest in future installments, but all it did was decrease the amount of space devoted to the main characters in this book. The secondary story about Macy's roommate and her boyfriend should have been greatly trimmed in favor of much greater character development of Macy and especially Leo. I never understood the main characters and more importantly, could not figure out what they saw in each other - especially Macy's interest in Leo because the guy never talked, he always just walked. He walked out every time something out of routine happened without saying a word. This would get old really fast. As far as I could tell Leo was interested in Macy because she was easy. And because the couple did not truly have what I would consider a real relationship at any time in the book - including the end, their sexual behavior was cheap adn tawdry and hardly what I am looking for even in a Blaze romance. I don't see this couple lasting longer than it takes for the flare of sexual attraction to pass.

First of all I'm not sure karenml read this book as every reference beginning with page one refers to the story taking place in TEXAS, not California, duh.

Secondly. Read This Book. I can't recommend it highly enough. I haven't read anything so kick[ing] in years. Can't wait for more of Ms. Kent's most excellent portrayal of city girls!

I am a woman and read this book for the benefit of my fiance and his daughter. While there were some excellent tips for figuring out a good strategy for winning custody battles, the examples of men's situations and numerous defeats was depressing! I was especially surprised by the number of men implying that their former spouses just suddenly went nuts and started acting crazy. If men can't get a CLUE, then they shouldn't get custody. If you're a man and you like the idea that women for the most part are stupid, bi-polar, and downright vindictive then you'll love this book. I do have to say that the advice given on looking for a good lawyer, and how to "act" in the courtroom were fairly good. If your ex is so awful that you feel propelled to read this book, I recommend "Joint Custody with a Jerk" instead.

This book was very well written and a valuable resource for fathers who have had their child kidnapped by an uncaring mother. The book exposes the judicial system for what it is-CORRUPT. Judges, lawyers, and their supporting cast are like the lions eating the Christians. Unfortunately, these despicable people have zero regard for children or other people, but only for the money that they can extract at the expense of other people's pain and conflict. It is ironic that those in charge of the judicial system should be the ones locked up behind bars for what they do is far more criminal than a typical crook. This book is good ammunition against these judical despots.

I just read the book and as a product of divorced parents I found it to be quite informative. I was comforted to learn that there are many, many people in my shoes. I would recommend this book to both people going through divorces, lawyers, and adult children of divorced parents.

I loved this book, back when it was called Jun Fan/Jeet Kune Do the textbook. That was Tim Tackett, Chris Kent production then. The pictures in this book are new but not as good or comprehensive as the Tackett/Kent book. My advice is get the Text Book version, and Pick up Tackett and Kent's Jeet Kune Do kickboxing book. Those are actually good. If you want to review techniques and understand alot of what goes into making a good JKD fighter. It is important to note that for that last part you must have read and absorbed the Tao of Jeet Kune Do.
Another complaint I have about this book, and is by no means minor, is the way Chris Kent handles grappling. It is quite clear to even a six month practicianer of, nearly any grappling art, except maybe Small Circle Jiu-jitsu, that Kent has no idea of what he is talking about. The problem is that Kent does not understand the grappling range at all. He seems to think it is a place where (after he has performed his miracle trapping) his opponent will just allow him to twist, crank, and lock him in any way Kent wants. There is no discussion of how dynamic this range is. Chris Kent, like Larry Harstell, can perform myriad locks and takedowns in the context of various drills, I am not sure they can do anything in a live situation. I am not saying they cannot, but the way they present their grappling, it appears that they really do not have an accurate idea of what happens when some one with skill crashes into you. I must say that is not the case with all JKD fighters (and in their defense, it may not be the case with Kent, and Hartstell). Roy Harris, Jack McVicker, Paul Vunak, Dion Riccardo, and Eric Paulson, and Dan Insosanto all understand what it is to really grapple. The point is from the Kent book I do not think he could handle a white belt of one year at any reputable bjj school.

This comprehensive book is very good. It explains Bruce Lee's art in a magnificent manner. There are over 650 photos along with tons of written information on the fighting techniques. They are really good and easy-to-learn. You can use the moves with complete confidence in a self-defense situation after just looking at the photos (seriously).

Everyone should have this book!

I own a copy of Chris Kent's book volume one and am going to purchase volume two. Financial and location difficulties only allow me a few months a year personal training with a Sifu in JKD so Mr. Kent's book helps me to practice movements and strategy in off months. It has good photos and text to help link the movements... extremely helpful. I mean it seems as Mr. Kent is right there helping you correct any problems in your techniques. It even has some grappling and holds as well which are essential to any martial artists skills.

Also Read: the Tao of JKD by Master Bruce Lee, and also Mr. Lee's several part series on different aspects of his philosophy , art and training methods. (I found Mr. Lee's training methods to be especially helpful , when I use them they improve my physical aspects and contemplating some of his thoughts help in life as well. Try some of Dr. Masaaki Hatsumi/Stephen Hayes Ninjutsu/Taijutsu books and Park Bok Nam's Pa Kua/Ba Gua series. I like these three arts b/c they are adaptive and efficient as arts and life styles in my humble opinion.

I cant stress stongly enough that buying this book is a waste of time and money. It is in total 76 pages long - 36 of which are completly blank log pages. So to the 40 pages of content - two of which are dedicated entirely on how to organise a brainstorming session - what the hell has that to do with SEO. Oh an by the way the only search engine they deal with is Alta Vista. At least hes honest.

Daniel

This book made is plain and simple for me on how to get organized and how to approach writing my web pages. I had seen stuff here and there on the internet but to have the nuts and bolts of it explained clearly helped me out. Great for a beginner just starting out.

Hi Everyone, thanks for the critiques, it will make our next book better! Terry and I actually wrote this little book for ourselves. We wrote it to help in our SEO efforts on our own web sites. We have used this book to promote several web sites. Let me tell you, this method works!

However, what I am really here to tell you is that, SEO is easy. Our book is VERY BASIC, because learning the essentials of SEO is easy. The book is a journal. There are tips on how to optimize, but it is more of a workbook to keep you organized, the key to a good SEO campaign is organization.

If you're looking for a technical book, this is not the book for you. This is the layman's way to SEO nirvana.